home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 6
/
Night Owl's Shareware - PDSI-006 - Night Owl Corp (1990).iso
/
049a
/
trimal21.zip
/
HISTORY.DOC
next >
Wrap
Text File
|
1991-06-21
|
3KB
|
133 lines
06/21/91 TriMail v2.1 is released.
TriMail's select conference queue routine has been
totally revamped. TriMail will display the queued
status of 30 conferences at a time and allow the caller
to select and deselect conferences. Additionally, the
caller can now set his last message read pointers.
Fixed a slight display bug in the download QWK packet
display. The columns weren't quite lined up correctly.
05/30/91 TriMail v2.0 is released.
TriMail can now produce RNet/MarkMail compatible net
status packets.
TriMail will now reset the user's last message read
pointers so that any REP files won't be included in the
user's QWK packet. You should note that TriMail is
clever enough to allow the user to upload his REP
packet first and then download a QWK packet without
losing all of the mail that comes before the REP
messages.
TriMail now indicates how many messages are addressed
to the user in each conference.
TriMail now prompts the user as to whether or not he
wants to download the QWK packet.
TriMail now displays the QWK packet's size and
estimated download time.
TriMail now checks to see if the user has enough
remaining time to download the QWK packet.
05/15/91 TriMail v1.1 is released.
Added support for TriTel v1.1's extended file
descriptions. The full description will now be listed
if the new file has a multiline description.
Added support for TriTel v1.1's newsletter. The
newsletter will optionally be added to the QWK packet
if it has been updated since the user's last call and
he has his configuration set to include the newsletter
in his QWK packets.
v1.0 would only allow user names with both a first and
last name. v1.1 will now allow both single names and
more than two names for the user. NOTE: Due to
limitations in the PCBoard door data file formats, only
the first two names are compared when trying to find
the caller in the user file. This could present a
problem if you have a caller whose first and last names
match the first and second names for a caller with more
than two names. This type of circumstance would
probably be rare, but I felt I should bring it to
everybody's attention. If this should happen, get the
two users to agree upon new names that won't conflict.
v1.1 would hang the system if a user's name wasn't
found in the user file. Fixed.